[One Click Apps] Deploy a custom application from a repository or an image
Deploy the customer’s own code on the instance platform: a public or private git repository (nixpacks, static, dockerfile or dockercompose build pack) or a Docker image. The platform must be ready, the name must be free on the instance and the RAM budget must allow one more application (custom applications are budgeted at the default RAM). The optional custom domain follows the same managed-zone rules as catalog applications. Initial environment variables are pushed before the first build. A private repository is cloned with the platform deploy key (see GET …/platform/deploy-key). The deployment runs asynchronously as an instance task; the task fails with the last build log lines when the build does not finish.
Authorizations
Use Authorization: Bearer <token> header. Token can be a JWT token or an API key (format: sk-onetsolutions-...).
Path Parameters
Unique identifier of the compute instance.
Unique identifier of the organization that owns the resource.
Unique identifier of the project containing the resource.

